Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add missing sys_chroot capability to groupadd policy #2316

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

pmatilai
Copy link
Contributor

Just like useradd, groupadd supports chroot operation, but for that to work it needs the sys_chroot capability, just like the useradd policy has (see commit 0651cc9).

This is one of the roadblocks in making RPM sysusers feature fully functional: rpm-software-management/rpm#3227

Just like useradd, groupadd supports chroot operation, but for that
to work it needs the sys_chroot capability, just like the useradd
policy has (see commit 0651cc9).

This is one of the roadblocks in making RPM sysusers feature fully
functional: rpm-software-management/rpm#3227
Copy link

Cockpit tests failed for commit 89491e6. @martinpitt, @jelly, @mvollmer please check.

@martinpitt
Copy link
Contributor

martinpitt commented Aug 26, 2024

This F41 cockpit failure is due to a coreutils/gnulib regression, see https://bugzilla.redhat.com/show_bug.cgi?id=2307847 . We created a naughty pattern ("failure due to OS regression") for that in cockpit-project/bots#6790 . This landed now, so the next run will be green again. You can retry or ignore here.

Update: I forgot that I can retry myself in this project, kicked.

@zpytela
Copy link
Contributor

zpytela commented Aug 26, 2024

Merging, thank you.

@zpytela zpytela merged commit eb38a88 into fedora-selinux:rawhide Aug 26, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants